Identifying equivalent JavaScript events

ABSTRACT

Identifying equivalent JavaScript events includes receiving source code containing two JavaScript events for equivalency analysis, extracting an HTML element containing an event from each JavaScript event and analyzing the extracted HTML elements. Responsive to a determination that the HTML elements are of a same type according to equivalency criteria B, and responsive to a determination that the HTML elements have a same number of attributes according to equivalency criteria C, a determination is made whether JavaScript function calls of each JavaScript event are similar according to equivalency criteria A. Responsive to a determination that the JavaScript function calls are similar according to equivalency criteria A, and responsive to a determination that the other attributes of the HTML elements satisfy equivalency criteria D, the JavaScript events are identified as equivalent.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of Canada Application Number 2786418filed on Aug. 16, 2012, which is fully incorporated herein by reference.

BACKGROUND

A website crawler is a tool that performs an automatic exploration of awebsite. This task is beneficial for many applications from a simpleindexing of information task, to more complex compliance testing, toname a few.

One of the challenges faced by automated tools is an ability todetermine whether two JavaScript events on a page perform equivalentactions. Equivalent in this sense means, executing the two JavaScriptevents independently to create a document object model (DOM) of the pagein which the two states are equivalent. Determining whether twoJavaScript events are equivalent is useful because websites providingservice such as news, blogs, on-line stores, and emails, have manyJavaScript actions that perform equivalent tasks.

In practice, there are normally several sets of equivalent events on agiven page, and each event from an equivalent set may lead to displayinga single news item, a single blog entry, a single item in a store, or asingle email. Each set may be referred to as a set of equivalentJavaScript events. Executing all possible equivalent JavaScript eventsof a website is a time consuming task that is not required in all cases.For example, when performing a security scan, a crawler is moreinterested in a structure of a webpage, than the text content of thewebpage. In this example, executing just one link in an equivalent setis typically enough, with results being generalized for every otherequivalent JavaScript action.

In addition, most websites on subsequent visits typically change the setof equivalent JavaScript events displayed to the user. Accordingly, anews site displays the latest news, a blog displays the latest blogs,and an on-line store displays the items on sale. The crawling of suchwebsites, is further complicated because the container page comprisingall equivalent JavaScript actions will never be the same, and thereforea crawler will not know that the current page was a previously visitedpage.

When a web crawler does not understand which JavaScript events areequivalent the crawler is typically not be able to identify whether thecurrent page was previously visited because the content inside the redbox has likely changed. The web crawler is typically unable to finishscanning a current website, because every action taken to modify asearch criteria brings new content on the page.

Current workarounds for the identified problem typically includelimiting a number of JavaScript actions executed on a page, orperforming a human guided exploration of the website. Other solutionstypically require the web crawler to execute JavaScript actions andcompare the two DOMs that result.

BRIEF SUMMARY

According to one embodiment, a computer-implemented process foridentifying equivalent JavaScript events receives source code containingtwo JavaScript events for equivalency analysis, extracts an HTML elementcontaining an event from each JavaScript event of the received sourcecode to form extracted elements and analyzes the extracted HTML elementsusing a processor. The computer-implemented process determines whetherthe HTML elements are of a same type according to equivalency criteria Band responsive to a determination that the HTML elements are of a sametype according to equivalency criteria B, determines whether the HTMLelements have a same number of attributes according to equivalencycriteria C. Responsive to a determination that the HTML elements have asame number of attributes according to equivalency criteria C, thecomputer-implemented process determines whether JavaScript functioncalls of each JavaScript event are similar according to equivalencycriteria A and responsive to a determination that the JavaScriptfunction calls are similar according to equivalency criteria A, thecomputer-implemented process determines whether other attributes of theHTML elements satisfy equivalency criteria D. Responsive to adetermination that the other attributes of the HTML elements satisfyequivalency criteria D, the computer-implemented process identifies theJavaScript events as equivalent.

According to another embodiment, a computer program product foridentifying equivalent JavaScript events comprises a computer readabledata storage medium containing computer executable program code storedthereon. The computer executable program code includes computerexecutable program code for receiving source code containing twoJavaScript events for equivalency analysis; computer executable programcode for extracting an HTML element containing an event from eachJavaScript event of the received source code to form extracted elements;computer executable program code for analyzing the extracted HTMLelements; computer executable program code for determining whether theHTML elements are of a same type according to equivalency criteria B;computer executable program code responsive to a determination that theHTML elements are of a same type according to equivalency criteria B,for determining whether the HTML elements have a same number ofattributes according to equivalency criteria C; computer executableprogram code responsive to a determination that the HTML elements have asame number of attributes according to equivalency criteria C, fordetermining whether JavaScript function calls of each JavaScript eventare similar according to equivalency criteria A; computer executableprogram code responsive to a determination that the JavaScript functioncalls are similar according to equivalency criteria A, for determiningwhether other attributes of the HTML elements satisfy equivalencycriteria D and computer executable program code responsive to adetermination that the other attributes of the HTML elements satisfyequivalency criteria D, for identifying the JavaScript events asequivalent.

According to another embodiment, an apparatus for identifying equivalentJavaScript events includes a processor programmed to initiate executableoperations. The executable operations include receiving source codecontaining two JavaScript events for equivalency analysis, extracting anHTML element containing an event from each JavaScript event of thereceived source code to form extracted elements and analyzing theextracted HTML elements. The executable operations further includedetermining whether the HTML elements are of a same type according toequivalency criteria B and responsive to a determination that the HTMLelements are of a same type according to equivalency criteria B,determining whether the HTML elements have a same number of attributesaccording to equivalency criteria C. The executable operations alsoinclude, responsive to a determination that the HTML elements have asame number of attributes according to equivalency criteria C,determining whether JavaScript function calls of each JavaScript eventare similar according to equivalency criteria A and responsive to adetermination that the JavaScript function calls are similar accordingto equivalency criteria A, determining whether other attributes of theHTML elements satisfy equivalency criteria D. Responsive to adetermination that the other attributes of the HTML elements satisfyequivalency criteria D, the JavaScript events are identified asequivalent.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

For a more complete understanding of this disclosure, reference is nowmade to the following brief description, taken in conjunction with theaccompanying drawings and detailed description, wherein like referencenumerals represent like parts.

FIG. 1 is a block diagram of an exemplary network data processing systemoperable for various embodiments of the disclosure;

FIG. 2 is a block diagram of an exemplary data processing systemoperable for various embodiments of the disclosure;

FIG. 3 is a block diagram of an identification system operable forvarious embodiments of the disclosure;

FIG. 4 is a code snippet representation a document object compliance ofequivalence requirements using the identification system of FIG. 3operable for various embodiments of the disclosure;

FIG. 5 is a code snippet representation a document object compliance ofequivalence requirements using the identification system of FIG. 3operable for various embodiments of the disclosure;

FIG. 6 is a flowchart of an event equivalency process using theidentification system of FIG. 3 operable for various embodiments of thedisclosure; and

FIG. 7 is a flowchart of crawling process integrating an eventequivalency process using the identification system of FIG. 3 operablefor various embodiments of the disclosure.

DETAILED DESCRIPTION

This disclosure relates generally to exploration of data in a dataprocessing system and more specifically to identifying equivalentJavaScript™ events in a predefined collection of data in the dataprocessing system.

Although an illustrative implementation of one or more embodiments isprovided below, the disclosed systems and/or methods may be implementedusing any number of techniques. This disclosure should in no way belimited to the illustrative implementations, drawings, and techniquesillustrated below, including the exemplary designs and implementationsillustrated and described herein, but may be modified within the scopeof the appended claims along with their full scope of equivalents.

As will be appreciated by one skilled in the art, aspects of the presentdisclosure may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present disclosure may take theform of an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module,” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer-readable data storage medium(s)may be utilized. A computer-readable data storage medium may be, forexample, but not limited to, an electronic, magnetic, optical, orsemiconductor system, apparatus, or device, or any suitable combinationof the foregoing. More specific examples (a non-exhaustive list) of thecomputer-readable data storage medium would include the following: aportable computer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a portable compact disc read-only memory (CDROM), anoptical storage device, or a magnetic storage device or any suitablecombination of the foregoing. In the context of this document, acomputer-readable data storage medium is any tangible medium that cancontain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

A computer-readable signal medium may include a propagated data signalwith the computer-readable program code embodied therein, for example,either in baseband or as part of a carrier wave. Such a propagatedsignal may take a variety of forms, including but not limited toelectro-magnetic, optical or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer-readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wire line, optical fiber cable, RF, etc. or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent disclosure may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java®, Smalltalk, C++, or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. Java and all Java-based trademarks and logos aretrademarks of Oracle, and/or its affiliates, in the United States, othercountries or both. The program code may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).

Aspects of the present disclosure are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus,(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions.

These computer program instructions may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer or other programmable dataprocessing apparatus to function in a particular manner, such that theinstructions stored in the computer readable medium produce an articleof manufacture including instructions which implement the function/actspecified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide processes for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

With reference now to the figures and in particular with reference toFIGS. 1-2, exemplary diagrams of data processing environments areprovided in which illustrative embodiments may be implemented. It shouldbe appreciated that FIGS. 1-2 are only exemplary and are not intended toassert or imply any limitation with regard to the environments in whichdifferent embodiments may be implemented. Many modifications to thedepicted environments may be made.

FIG. 1 depicts a pictorial representation of a network of dataprocessing systems in which illustrative embodiments may be implemented.Network data processing system 100 is a network of computers in whichthe illustrative embodiments may be implemented. Network data processingsystem 100 contains network 102, which is the medium used to providecommunications links between various devices and computers connectedtogether within network data processing system 100. Network 102 mayinclude connections, such as wire, wireless communication links, orfiber optic cables.

In the depicted example, server 104 and server 106 connect to network102 along with storage unit 108. In addition, clients 110, 112, and 114connect to network 102. Clients 110, 112, and 114 may be, for example,personal computers or network computers. In the depicted example, server104 provides data, such as boot files, operating system images, andapplications to clients 110, 112, and 114. Clients 110, 112, and 114 areclients to server 104 in this example. Network data processing system100 may include additional servers, clients, and other devices notshown.

In the depicted example, network data processing system 100 is theInternet with network 102 representing a worldwide collection ofnetworks and gateways that use the Transmission ControlProtocol/Internet Protocol (TCP/IP) suite of protocols to communicatewith one another. At the heart of the Internet is a backbone ofhigh-speed data communication lines between major nodes or hostcomputers, consisting of thousands of commercial, governmental,educational and other computer systems that route data and messages. Ofcourse, network data processing system 100 also may be implemented as anumber of different types of networks, such as for example, an intranet,a local area network (LAN), or a wide area network (WAN). FIG. 1 isintended as an example, and not as an architectural limitation for thedifferent illustrative embodiments.

With reference to FIG. 2 a block diagram of an exemplary data processingsystem operable for various embodiments of the disclosure is presented.In this illustrative example, data processing system 200 includescommunications fabric 202, which provides communications betweenprocessor unit 204, memory 206, persistent storage 208, communicationsunit 210, input/output (I/O) unit 212, and display 214.

Processor unit 204 serves to execute instructions for software that maybe loaded into memory 206. Processor unit 204 may be a set of one ormore processors or may be a multi-processor core, depending on theparticular implementation. Further, processor unit 204 may beimplemented using one or more heterogeneous processor systems in which amain processor is present with secondary processors on a single chip. Asanother illustrative example, processor unit 204 may be a symmetricmulti-processor system containing multiple processors of the same type.

Memory 206 and persistent storage 208 are examples of storage devices216. A storage device is any piece of hardware that is capable ofstoring information, such as, for example without limitation, data,program code in functional form, and/or other suitable informationeither on a temporary basis and/or a permanent basis. Memory 206, inthese examples, may be, for example, a random access memory or any othersuitable volatile or non-volatile storage device. Persistent storage 208may take various forms depending on the particular implementation. Forexample, persistent storage 208 may contain one or more components ordevices. For example, persistent storage 208 may be a hard drive, aflash memory, a rewritable optical disk, a rewritable magnetic tape, orsome combination of the above. The media used by persistent storage 208also may be removable. For example, a removable hard drive may be usedfor persistent storage 208.

Communications unit 210, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 210 is a network interface card. Communications unit210 may provide communications through the use of either or bothphysical and wireless communications links.

Input/output unit 212 allows for input and output of data with otherdevices that may be connected to data processing system 200. Forexample, input/output unit 212 may provide a connection for user inputthrough a keyboard, a mouse, and/or some other suitable input device.Further, input/output unit 212 may send output to a printer. Display 214provides a mechanism to display information to a user.

Instructions for the operating system, applications and/or programs maybe located in storage devices 216, which are in communication withprocessor unit 204 through communications fabric 202. In theseillustrative examples the instructions are in a functional form onpersistent storage 208. These instructions may be loaded into memory 206for execution by processor unit 204. The processes of the differentembodiments may be performed by processor unit 204 usingcomputer-implemented instructions, which may be located in a memory,such as memory 206.

These instructions are referred to as program code, computer usableprogram code, or computer readable program code that may be read andexecuted by a processor in processor unit 204. The program code in thedifferent embodiments may be embodied on different physical or tangiblecomputer readable storage media, such as memory 206 or persistentstorage 208.

Program code 218 is located in a functional form on computer readablestorage media 220 that is selectively removable and may be loaded ontoor transferred to data processing system 200 for execution by processorunit 204. Program code 218 and computer readable storage media 220 formcomputer program product 222 in these examples. In one example, computerreadable storage media 220 may be in a tangible form, such as, forexample, an optical or magnetic disc that is inserted or placed into adrive or other device that is part of persistent storage 208 fortransfer onto a storage device, such as a hard drive that is part ofpersistent storage 208. In a tangible form, computer readable storagemedia 220 also may take the form of a persistent storage, such as a harddrive, a thumb drive, or a flash memory that is connected to dataprocessing system 200. The tangible form of computer readable storagemedia 220 is also referred to as computer recordable storage media. Insome instances, computer readable storage media 220 may not beremovable.

Alternatively, program code 218 may be transferred to data processingsystem 200 from computer readable storage media 220 through acommunications link to communications unit 210 and/or through aconnection to input/output unit 212. The communications link and/or theconnection may be physical or wireless in the illustrative examples. Thecomputer readable media also may take the form of non-tangible media,such as communications links or wireless transmissions containing theprogram code.

In some illustrative embodiments, program code 218 may be downloadedover a network to persistent storage 208 from another device or dataprocessing system for use within data processing system 200. Forinstance, program code stored in a computer readable storage medium in aserver data processing system may be downloaded over a network from theserver to data processing system 200. The data processing systemproviding program code 218 may be a server computer, a client computer,or some other device capable of storing and transmitting program code218.

Using data processing system 200 of FIG. 2 as an example, acomputer-implemented process for identifying equivalent JavaScriptevents is presented. The disclosed process enables a web crawler toprogrammatically determine when two or more JavaScript actions areequivalent. Use of embodiments of the disclosed process does not requireJavaScript actions to be executed upfront to detect equivalency.

Processor unit 204 receives source code containing two JavaScript eventsfor equivalency analysis, using communications unit 210, input/outputunit 212 or storage devices 216, extracts an HTML element containing anevent from each JavaScript event of the received source code to formextracted elements and analyzes the extracted HTML elements. Processorunit 204 determines whether the HTML elements are of a same typeaccording to equivalency criteria B and responsive to a determinationthat the HTML elements are of a same type according to equivalencycriteria B, determines whether the HTML elements have a same number ofattributes according to equivalency criteria C. Processor unit 204responsive to a determination that the HTML elements have a same numberof attributes according to equivalency criteria C, determines whetherJavaScript function calls of each JavaScript event are similar accordingto equivalency criteria A and responsive to a determination that theJavaScript function calls are similar according to equivalency criteriaA, processor unit 204 determines whether other attributes of the HTMLelements satisfy equivalency criteria D. Responsive to a determinationthat the other attributes of the HTML elements satisfy equivalencycriteria D, processor unit 204 identifies the JavaScript events asequivalent. The identified equivalent JavaScript events may be saved instorage devise 216 for subsequent processing or made available to otherapplications through communications unit 210.

With reference to FIG. 3 a block diagram of an identification systemoperable for various embodiments of the disclosure is presented.Identification system 300 is an example of an equivalency identificationsystem of an embodiment of the disclosure.

Identification system 300 comprises a number of component operations ofa functional unit leveraging underlying services of a data processingsuch as network data processing 100 of FIG. 1 or data processing system200 of FIG. 2. Identification system 300 may be implemented as acollection of discrete components in an interdependent relationship inwhich the components are operatively coupled to exchange data or as amonolithic entity embodying the functional components without affectingthe functional capability of the disclosed process.

Identification system 300 provides a capability of identifyingequivalent JavaScript events using a collection of cooperativecomponents comprising crawler 302, analyzer 304, rules 306, generator308, repository 310 and reporter 312. Identification system 300 providesa package, which may be implemented as an enhancement to a currentcrawler or as a new function to an existing system. The example using aweb crawler is one embodiment; alternative embodiments include a dataexplorer capability for analyzing data for example when indexing non-webbased data. Accordingly the disclosed process is not restricted to usein only a web-based environment of the example.

Crawler 302 provides a capability of a conventional web crawler with anadded ability to perform the added function of the disclosed process. Inan embodiment the disclosed process is integrated within an existing webcrawler, but as mentioned the function of a crawler with the disclosedprocess may be used in a non web-based environment equally well.

Analyzer 304 provides a capability of a parser and a comparator toexamine provided data to determine equivalency of pairs of JavaScriptevents. A parser portion of analyzer 304 traverses input code toidentify relevant information such as predetermined HTML tags andcorresponding attributes of the identified HTML tags. A comparatorportion of analyzer 304 compares the portions of each event in the pairsof JavaScript events according to predefined criteria in rules 306.Rules 306 is a collection of specifications defining criteria underwhich equivalency is determined. Rules 306 provide specification of theindividual conditions, which combine to define the equivalencyrequirement criteria against which the pairs of JavaScript events areevaluated. Examples of rules forming rules 306 are provided in relationto FIG. 4.

Generator 308 provides a capability to create a document object modelusing information associated with a JavaScript event being evaluated.For example a new document object model (DOM) is constructed after anevent is executed.

Repository 310 provides a capability to persist information used withinthe disclosed process and to contain results available to users of thedisclosed process. Repository 310 provides a storage locationinformation associated with the disclosed process including for example,intermediate results, generated DOMs, and final results ofidentification, for example a list of equivalent JavaScript events.

Reporter 312 provides a capability to generate output of the results ofthe identification process of identification system 300 for use byothers, including applications. For example a simple list of equivalentJavaScript events may be made available or a path name for a locationwithin a file or database instance may be provided as required by anembodiment.

With reference to FIG. 4 a code snippet representation a document objectcompliance of equivalence requirements operable for various embodimentsof the disclosure is presented. Code snippet 400 is an example ofJavaScript event equivalence using the identification system 300 of FIG.3.

Embodiments of the disclosure use the following definition of JavaScriptevent equivalence criteria. JavaScript event 1 is equivalent withJavaScript event 2 when the pair events satisfy all of the requirementsfor equivalence. Equivalence criteria A require equivalent JavaScriptactions will follow a similar JavaScript function call pattern (forexample as portions 406, 408 and 410). Equivalence accordingly requirescalls to have the same function name, the number of parameters and thesame parameter types with different or equal parameter values.Optionally a static analysis of the function body can be performed.However, the static analysis of the function body is not required for anembodiment of the proposed process.

Equivalence criteria B require the HTML elements that contain theequivalent JavaScript actions are always of the same HTML element type(for example, elements of portions 404). Equivalence criteria C requirethe HTML elements that contain the equivalent JavaScript actions havethe same number of other HTML attributes (for example, elements ofportion 402).

Equivalence criteria D require all other attribute values for the HTMLelement that contains the JavaScript action to satisfy the criteria ofwhen the values are non-JavaScript calls, the calls need to have thesame values and when the values are JavaScript calls/actions, thecalls/actions need to comply with previously defined criteria A. Note,there are a few attributes that will be an exception to this rule forexample HTML elements including id, alt, title, coordinates, because therespective value is expected to change between different entries.Therefore, any attribute that refers to a position (for example,coordinate), further explains the information contained in the HTMLelement (for example, alt, title), or uniquely identifies an entry (forexample, id) should be excluded from this rule.

An embodiment of the process for JavaScript event equivalency can beexecuted against events that are on the same DOM of a page or an Ajaxstate. Furthermore, an embodiment of the event equivalency process canalso be executed on different DOMs that are extracted from differentAjax states or different DOMs of the same Ajax state but at differenttime intervals.

The event equivalence process determines for 2 events to be equivalentthe pair of events need to satisfy all equivalency requirements ofcriteria A, B, C and D and when at least one of the stated requirementsis not satisfied, the two events cannot be equivalent. The equivalencyfunction needs to be applied for every pair of JavaScript events fromthe pool of events needing analysis. The events can belong to the sameDOM or to separate DOMs.

Applying the equivalence requirements criteria A, B, C and D incombination to the example of code snippet 400 indicate events can begrouped into a set of equivalent events that follow a pattern. In theexample the pattern is shown in statement 412, as <ahref=“javascript:ajaxFunction(‘myevent’,1413)”>. This pattern has asimilar JavaScript function call across the statements in the form of:javascript:ajaxFunction(‘myevent’,xxx), contained within <a> HTMLelements, wherein the <a> elements have one attribute (for example,href) for all instances.

Note that for this particular website of the example, when a searchaction is selected, the content of the DOM will bring new equivalentevents, and therefore, understanding that the new events are equivalentwith the previous events helps the crawler to uniquely identify acontainer page. In addition, subsequent visits to the webpage will givedifferent equivalent events when new entries are added in the database.

With reference to FIG. 5 a code snippet representation a document objectcompliance of equivalence requirements operable for various embodimentsof the disclosure is presented. Code snippet 500 is an example ofJavaScript event equivalence using the identification system 300 of FIG.3.

Applying equivalency requirement criteria of A, B, C and D to theexample of code snippet 500 shows that events can be grouped into twosets of equivalent events that have a first set of equivalent eventsfollowing a pattern in statement 514 of <ahref=“javascript:openDeck(xxx);”>. The events have a similar JavaScriptfunction call in the form of javascript:ajaxFunction(‘myevent’,xxx),(for example, portion 504 of a call javascript:openDeck(570)) the eventsare contained within <a> HTML elements 506, and the <a> elements haveone attribute (for example, HTML element 508 of href) for all instances.

A second set of equivalent events follow a next pattern as in statement516, for example, a set of HTML elements 508 of an HTML element 506 ofarea as in:

<area coords=“xxx” shape=“poly” onclick=“openDeck(yyy)” alt=“zzz”class=“jTip” id=“www”>

These equivalent actions have a similar JavaScript function call inpattern 502 in the form of openDeck(yyy), they are contained in <area>HTML elements 506, the <area> elements have a set of six attributes (forexample, HTML elements 508 comprising cords, shape, onclick, alt, class,id) for all instances. Finally, attributes that do not refer to aposition, further explain information contained in the HTML element, oruniquely identify the entry, have the same values. In this example, HTMLelements 508 attributes of shape and class have respective values ofpoly 510 and jTip 512.

Embodiments of the disclosed process accordingly do not rely on userinput; rather conditions of requirement criteria A, B, C and D whichcomprise expert knowledge equivalency observations, are used toprogrammatically identify equivalent JavaScript actions. Furthermore,embodiments of the JavaScript equivalency process disclosed can beapplied on JavaScript actions that belong to the same or different Ajaxstates. When using embodiments of the disclosed process, execution ofJavaScript actions is not required to infer JavaScript actions areequivalent.

With reference to FIG. 6 a flowchart of an event equivalency processoperable for various embodiments of the disclosure is presented. Process600 is an example of an event equivalency process using identificationsystem 300 of FIG. 3. Process 600 can be applied each time a crawlerneeds to determine whether two JavaScript events are equivalent.

Process 600 begins (step 602) and receives two events to analyze forequivalency (step 604). When receiving source code containing twoJavaScript events for equivalency analysis, the two events may have beenpreviously selected from a pool of events or may be provided as next twoevents in a predetermined order or any other selection process providingpairs of event for analysis. Process 600 extracts an HTML elementcontaining the event from each received event to form extracted HTMLelements (step 606). Process 600 analyzes the extracted HTML elementscontaining the JavaScript event from each received event of the receivedsource code containing two JavaScript events for equivalency analysis(step 608).

Process 600 determines whether the two HTML elements are of a same typeaccording to equivalency criteria B (step 610). The two HTML elementsextracted in step 606 are involved in the comparison operation.Responsive to a determination that the two HTML elements are not of asame type according to equivalency criteria B, process 600 terminates(step 620).

Responsive to a determination that the two HTML elements are of a sametype according to equivalency criteria B, process 600 determines whetherthe two HTML elements have a same number of attributes according toequivalency criteria C (step 612). Responsive to a determination thatthe two HTML elements do not have a same number of attributes accordingto equivalency criteria C, process 600 terminates (step 620).

Responsive to a determination that the two HTML elements have a samenumber of attributes according to equivalency criteria C, process 600determines whether the two JavaScript function calls are similaraccording to equivalency criteria A (step 614). Responsive to adetermination that the two JavaScript function calls are not similaraccording to equivalency criteria A, process 600 terminates (step 620).

Responsive to a determination that the two JavaScript function calls aresimilar according to equivalency criteria A, process 600 determineswhether other attributes of the two HTML elements satisfy equivalencycriteria D (step 616). Responsive to a determination that the otherattributes of the two HTML elements do not satisfy equivalency criteriaD, process 600 terminates (step 620).

Responsive to a determination that the other attributes of the two HTMLelements satisfy equivalency criteria D, process 600 identifies the twoJavaScript events as equivalent (step 618) and terminates thereafter(step 620).

With reference to FIG. 7 a flowchart of crawling process integrating anevent equivalency process operable for various embodiments of thedisclosure is presented. Process 700 is an example of a crawling processintegrating an event equivalency process using identification system 300of FIG. 3. The event equivalency process is integrated in the crawlingprocess of a website. The flowchart mimics a general exploration task atypical web crawler performs. The exploration strategy of such websitesis out of the scope of the current disclosure.

Process 700 begins (step 702) and determines whether a crawler visitedall required universal resource locators (URLs) (step 704). Responsiveto a determination that a crawler visited all required universalresource locators, process 700 terminates (step 730). Responsive to adetermination that a crawler has not visited all required universalresource locators, process 700 goes to a next URL to be crawled to forma current URL (step 706). The next URL to be crawled is identified in atypical identification process known in the art of crawling web pages ofthe example.

Process 700 performs an equivalency analysis to identify equivalent setsof events using the current URL (step 708). The equivalency analysisused to identify equivalent sets of events using the current URL isprocess 600 of FIG. 6. Process 700 determines whether the crawlervisited the current URL (step 710). The results of the equivalencyanalysis provide input to the determination sub-process of step 710.

Responsive to a determination that the crawler visited the current URL,process 700 loops back to perform step 704 as before. Responsive to adetermination that the crawler has not visited the current URL, process700 determines whether a Web 2.0 exploration is required (step 712). Aspreviously stated, Web sites using Web 2.0 typically have a high numberof equivalent JavaScript operations.

Responsive to a determination that Web 2.0 exploration is not requiredprocess 700 performs usual crawling tasks using the current URL (step728). Process 700 loops back to perform step 704 as before. Responsiveto a determination that Web 2.0 exploration is required process 700determines whether the crawler executed all required JavaScript events(step 714). Responsive to a determination that the crawler executed allrequired JavaScript events, process 700 loops back to perform step 728as before.

Responsive to a determination that the crawler executed all requiredJavaScript events, process 700 selects a next JavaScript to be executed(step 716). Process 700 constructs a new document object model (DOM)after execution of the event (step 718). Process 700 determines whetherJavaScript events in the new DOM belong to an equivalency set previouslydiscovered (step 720). Discovery may include a lookup in a database or aname comparison performed using members of a list or other suitablemeans to review events that have been found to be equivalent.

Responsive to a determination those JavaScript events in the new DOM donot belong to an equivalency set previously discovered, process 700forms a new equivalency set (step 724). A new equivalency set may beformed for each new pattern identified, wherein events matching adefined pattern are added to the set previously formed. Responsive to adetermination that JavaScript events in the new DOM belong to anequivalency set previously discovered, process 700 determines whetherthe crawler visited the current state (step 722). When a crawlerdetermines the same URL or the same state was previously visited in step722, the crawler considers the set of equivalent events. Thisconsideration enables cases when those equivalent events change in thewebpage over time to be handled.

Responsive to a determination that the crawler visited the currentstate, process 700 loops back to perform step 714 as before. Responsiveto a determination that the crawler has not visited the current state,process 700 performs usual crawling tasks using the current state (step726), with process 700 looping back to perform step 714 as before. Acurrent state and a current URL may be used interchangeably.

A crawler may choose to execute one event or all equivalent events perequivalence class identified. For example, when security testing, oneevent per equivalence class would be sufficient, because the events willexpose the same structure, whereas, when crawling for indexing executingall events per equivalence class is necessary because the events willexpose different content.

After defining classes of equivalent events, execution of at least tworandom events for each equivalence class to determine whether theexecution yields equivalent states may be performed. The execution checkis useful for identifying webpage menus implemented using equivalentfunctions, which are not functionally equivalent because menu itemstypically yield two states that will not be equivalent. All events fromthis particular equivalence class need to be marked as not beingequivalent.

Function name and parameters are of little use for JavaScript attachedevents (for example, event handlers added to an element usingaddEventListener( ) or attachEvent( ), because the function is usuallyanonymous, meaning the function has no name and an empty parameter list.The body of the function however can be converted to a string for thecomparison. When dealing with cases, particularly with JavaScriptframeworks, where function equivalence is too weak, other conditions onan element tag and attributes may provide distinguishing information.

Thus is presented in an illustrative embodiment a computer-implementedprocess for identifying equivalent JavaScript events receives sourcecode containing two JavaScript events for equivalency analysis, extractsan HTML element containing an event from each JavaScript event of thereceived source code to form extracted elements and analyzes theextracted HTML elements. The computer-implemented process determineswhether the HTML elements are of a same type according to equivalencycriteria B and responsive to a determination that the HTML elements areof a same type according to equivalency criteria B, determines whetherthe HTML elements have a same number of attributes according toequivalency criteria C. Responsive to a determination that the HTMLelements have a same number of attributes according to equivalencycriteria C, the computer-implemented process determines whetherJavaScript function calls of each JavaScript event are similar accordingto equivalency criteria A and responsive to a determination that theJavaScript function calls are similar according to equivalency criteriaA, the computer-implemented process determines whether other attributesof the HTML elements satisfy equivalency criteria D. Responsive to adetermination that the other attributes of the HTML elements satisfyequivalency criteria D, the computer-implemented process identifies theJavaScript events as equivalent.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing a specified logical function. It should also be noted that,in some alternative implementations, the functions noted in the blockmight occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

The invention can take the form of an entirely hardware embodiment, anentirely software embodiment or an embodiment containing both hardwareand software elements. In a preferred embodiment, the invention isimplemented in software, which includes but is not limited to firmware,resident software, microcode, and other software media that may berecognized by one skilled in the art.

It is important to note that while the present invention has beendescribed in the context of a fully functioning data processing system,those of ordinary skill in the art will appreciate that the processes ofthe present invention are capable of being distributed in the form of acomputer readable data storage medium having computer executableinstructions stored thereon in a variety of forms. Examples of computerreadable data storage media include recordable-type media, such as afloppy disk, a hard disk drive, a RAM, CD-ROMs, DVD-ROMs. The computerexecutable instructions may take the form of coded formats that aredecoded for actual use in a particular data processing system.

A data processing system suitable for storing and/or executing computerexecutable instructions comprising program code will include at leastone processor coupled directly or indirectly to memory elements througha system bus. The memory elements can include local memory employedduring actual execution of the program code, bulk storage, and cachememories which provide temporary storage of at least some program codein order to reduce the number of times code must be retrieved from bulkstorage during execution.

Input/output or I/O devices (including but not limited to keyboards,displays, pointing devices, etc.) can be coupled to the system eitherdirectly or through intervening I/O controllers.

Network adapters may also be coupled to the system to enable the dataprocessing system to become coupled to other data processing systems orremote printers or storage devices through intervening private or publicnetworks. Modems, cable modems, and Ethernet cards are just a few of thecurrently available types of network adapters.

What is claimed is:
 1. A computer-implemented process for identifyingequivalent JavaScript events, comprising: receiving source codecontaining two JavaScript events; extracting, to form extracted HTMLelements, an HTML element containing an event from each of the twoJavaScript events; and identifying that the two JavaScript events areequivalent based upon: a determination that the extracted HTML elementsare of a same type according to equivalency criteria B, a determinationthat the extracted HTML elements have a same number of attributesaccording to equivalency criteria C, a determination that JavaScriptfunction calls of each of the two JavaScript events are similaraccording to equivalency criteria A, and a determination that otherattributes of the extracted HTML elements satisfy equivalency criteriaD.
 2. The process of claim 1, wherein the equivalency criteria Bincludes the extracted HTML elements having a same HTML element type. 3.The process of claim 1, wherein the equivalency criteria A includes theJavaScript actions follow a similar JavaScript function call pattern,and the function call pattern requires JavaScript function calls to havea same function name, number of parameters, and same parameter typeswith different or equal parameter values.
 4. The process of claim 1,wherein the equivalency criteria C requires the extracted HTML elementshave a same number of other HTML attributes.
 5. The process of claim 1,wherein the equivalency criteria D requires all other attribute valuesfor the HTML element satisfy a criteria that upon the attribute valuesare non-JavaScript calls, the non-JavaScript calls have the same valuesand upon the attribute values are JavaScript calls/actions, theJavaScript calls/actions comply with equivalency criteria A.
 6. Theprocess of claim 1, wherein the received source code is for web-basedinformation or non-web-based information.
 7. The process of claim 1,wherein the identifying is part of a crawling process of a website.
 8. Acomputer program product for identifying equivalent JavaScript events,comprising: a computer readable data storage device containing computerexecutable program code stored thereon, the computer executable programcode, which when executed by a computer hardware device, causes thecomputer hardware device to perform: receiving source code containingtwo JavaScript events; extracting, to form extracted HTML elements, anHTML element containing an event from each of the two JavaScript events;and identifying that the two JavaScript events are equivalent basedupon: a determination that the extracted HTML elements are of a sametype according to equivalency criteria B, determination that theextracted HTML elements have a same number of attributes according toequivalency criteria C, a determination that JavaScript function callsof each of the two JavaScript events are similar according toequivalency criteria A, and a determination that other attributes of theextracted HTML elements satisfy equivalency criteria D.
 9. The computerprogram product of claim 8, wherein the equivalency criteria B includesthe extracted HTML elements having a same HTML element type.
 10. Thecomputer program product of claim 8, wherein the equivalency criteria Aincludes the JavaScript actions follow a similar JavaScript functioncall pattern, and the function call pattern requires JavaScript functioncalls to have a same function name, number of parameters, and sameparameter types with different or equal parameter values.
 11. Thecomputer program product of claim 8, wherein the equivalency criteria Crequires the extracted HTML elements have a same number of other HTMLattributes.
 12. The computer program product of claim 8, wherein theequivalency criteria D requires all other attribute values for the HTMLelement satisfy a criteria that upon the attribute values arenon-JavaScript calls, the non-JavaScript calls have the same values andupon the attribute values are JavaScript calls/actions, the JavaScriptcalls/actions comply with equivalency criteria A.
 13. The computerprogram product of claim 8, wherein the received source code is forweb-based information or non-web-based information.
 14. The computerprogram product of claim 8, wherein the identifying is part of acrawling process of a website.
 15. An apparatus for identifyingequivalent JavaScript events, comprising: a hardware processorconfigured to initiate the following executable operations: receivingsource code containing two JavaScript events; extracting, to formextracted HTML elements, an HTML element containing an event from eachof the two JavaScript events; and identifying that the two JavaScriptevents are equivalent based upon: a determination that the extractedHTML elements are of a same type according to equivalency criteria B, adetermination that the extracted HTML elements have a same number ofattributes according to equivalency criteria C, a determination thatJavaScript function calls of each of the two JavaScript events aresimilar according to equivalency criteria A, and a determination thatother attributes of the extracted HTML elements satisfy equivalencycriteria D.
 16. The apparatus of claim 15, wherein the equivalencycriteria B includes the extracted HTML elements having a same HTMLelement type.
 17. The apparatus of claim 15, wherein the equivalencycriteria A includes the JavaScript actions follow a similar JavaScriptfunction call pattern, and the function call pattern requires JavaScriptfunction calls to have a same function name, number of parameters, andsame parameter types with different or equal parameter values.
 18. Theapparatus of claim 15, wherein the equivalency criteria C requires theextracted HTML elements have a same number of other HTML attributes. 19.The apparatus of claim 15, wherein the equivalency criteria D requiresall other attribute values for the HTML element satisfy a criteria thatupon the attribute values are non-JavaScript calls, the non-JavaScriptcalls have the same values and upon the attribute values are JavaScriptcalls/actions, the JavaScript calls/actions comply with equivalencycriteria A.
 20. The apparatus of claim 15, wherein the received sourcecode is for web-based information or non-web-based information.